Quality of Service (QoS) support includes setting QoS DSCP trust and defining & applying the QoS PCP and DSCP ingress and egress maps on Ethernet interfaces and Port Channels.
Tip
As a best practice, avoid running user-driven policy operations in parallel with fabric, tenant, port channel, and tenant endpoint group operations.To ensure that the fabric, tenant, port channel, and tenant endpoint group configurations are effective, run the show command before proceeding with the policy operations, and vice-versa.
QoS support in XCO 3.4.0 is as follows.
Product ID | SLX Version |
---|---|
SLX 9150/SLX 9250 | 20.4.3 or higher |
Extreme 8720 | 20.4.3 or higher |
Extreme 8520 | 20.4.3 or higher |
SLX-9740 | 20.5.2 Partial support: Egress DSCP maps not supported. |
Extreme 8820 | 20.5.2 Partial support: Egress DSCP maps not supported. |
SLX-9540 | No support |
SLX-9640 | No support |
There are two ways you can implement quality of service (QoS) in XCO:
QoS map defines mapping of header fields to QoS traffic classes on the device.
The following header fields are considered for classification:
You can map each of the header fields with the eight different traffic classes TC0-TC7. You can define QoS maps for mapping.
For egress traffic, you can also specify the mapping between TC to PCP or DSCP field in the QoS maps. For example, you can define classification based on DSCP bits in the IP Header of the incoming packets. Each of the 64 DSCP values can be mapped to any one of the eight traffic classes.
A QoS profile is a collection of information that can be applied on an interface or device that controls the queuing and dequeuing of traffic flow based on packet header information or internal queuing. QoS Profile defines the following:
The information includes global, interface, and flow configurations. The profile is a list of rules that define a desired QoS behavior.
QoS profile is supported only for the physical interfaces. PO, VE, and breakout ports do not support QoS profile.
You can use a QoS profile to define the classification and actions applied to the traffic such as the following:
There are two ways you can implement quality of service (QoS) in XCO:
QoS map defines mapping of header fields to QoS traffic classes on the device.
The following header fields are considered for classification:
You can map each of the header fields with the eight different traffic classes TC0-TC7. You can define QoS maps for mapping.
For egress traffic, you can also specify the mapping between TC to PCP or DSCP field in the QoS maps. For example, you can define classification based on DSCP bits in the IP Header of the incoming packets. Each of the 64 DSCP values can be mapped to any one of the eight traffic classes.
QoS service policy maps are used to define policies for scheduling, policing, and shaping network traffic.
XCO 3.4.0 allows you to implement scheduling policies for better management of network traffic. With XCO 3.4.0, you can assign strict priority to certain traffic class queues while using DWRR (Deficit Weighted Round Robin) with customized weights for other traffic class queues.
This enables you to efficiently manage network traffic and ensure that high-priority traffic is given the appropriate amount of bandwidth.
You can associate a QoS service policy map with a QoS profile by providing its name. Once associated, the policy settings (such as strict priority and DWRR) will be applied to all ports that the QoS profile is bound to.
Configuration | Identify drift | Reconcile configuration | Idempotency |
---|---|---|---|
QoS Maps | Yes | Yes | No |
QoS Profile | Yes | Yes | No |